Context: dotnet/android#9630

As #9630 required new declarations of
`DynamicallyAccessedMemberTypes.Interfaces`, we intestigated to see
*why* these were needed in Java.Interop.

There are two cases:

    var listIface   = typeof (IList<>);
    var listType    =
        (from iface in type.GetInterfaces ().Concat (new[]{type})
            where (listIface).IsAssignableFrom (iface.IsGenericType ? iface.GetGenericTypeDefinition () : iface)
            select iface)
        .FirstOrDefault ();

This first one, if `IList<>` were trimmed away. We don't actually
care, as everything in this code path would still work. We can
suppress the warning instead.

The second case:

    JniValueMarshalerAttribute? ifaceAttribute = null;
    foreach (var iface in type.GetInterfaces ()) {
        marshalerAttr = iface.GetCustomAttribute<JniValueMarshalerAttribute> ();
        if (marshalerAttr != null) {
            if (ifaceAttribute != null)
                throw new NotSupportedException ($"There is more than one interface with custom marshaler for type {type}.");

            ifaceAttribute = marshalerAttr;
        }
    }
    if (ifaceAttribute != null)
        return (JniValueMarshaler) Activator.CreateInstance (ifaceAttribute.MarshalerType)!;

Feels like we should be able to remove this code completely.

With these changes we can remove `DynamicallyAccessedMemberTypes.Interfaces`.

I also introduced `build-tools/trim-analyzers/trim-analyzers.props`
that will setup the appropriate trimmer MSBuild properties to make
trimmer warnings an error. This should keep us from accidentally
creating warnings. I only use this setting in projects that were
already using `$(EnableAotAnalyzer)`.

)

Context: dotnet/android#9630
Context: ec2813a

As dotnet/android#9630 required new declarations of
`DynamicallyAccessedMemberTypes.Interfaces`, we intestigated to see
*why* these were needed in Java.Interop.

There are two cases that involve `.Interfaces` within 
`JniRuntime.JniValueManager.GetValueMarshaler(Type)`:

The first case is around attempts to special-case array marshaling
for builtin types:

	var listIface   = typeof (IList<>);
	var listType    =
	    (from iface in type.GetInterfaces ().Concat (new[]{type})
	        where (listIface).IsAssignableFrom (iface.IsGenericType ? iface.GetGenericTypeDefinition () : iface)
	        select iface)
	    .FirstOrDefault ();

If `IList<T>` is trimmed away (lol), then *we don't care*, as
everything else within `GetValueMarshaler(Type)` still works,
and if we can't get a value marshaler for `int[]` (which implements
`IList<T>`!), then so be it.  Suppress this IL2070 message.

The second case is around looking for `[JniValueMarshaler]` on
implemented interface types, from ec2813a:

	JniValueMarshalerAttribute? ifaceAttribute = null;
	foreach (var iface in type.GetInterfaces ()) {
	    marshalerAttr = iface.GetCustomAttribute<JniValueMarshalerAttribute> ();
	    if (marshalerAttr != null) {
	        if (ifaceAttribute != null)
	            throw new NotSupportedException ($"There is more than one interface with custom marshaler for type {type}.");

	        ifaceAttribute = marshalerAttr;
	    }
	}
	if (ifaceAttribute != null)
	    return (JniValueMarshaler) Activator.CreateInstance (ifaceAttribute.MarshalerType)!;

It is to support the scenario

	namespace Android.Runtime {
	    [JniValueMarshaler(typeof(IJavaObjectValueMarshaler))]
	    partial interface /* Android.RuntimIJavaObject {}
	}
	namespace Java.Lang {
	    partial class Object : Android.Runtime.IJavaObject {}
	}

to "retrofit" `Java.Lang.Object` and `Java.Lang.Throwable` to use
`IJavaObjectValueMarshaler`.

There are three problems with this case:

 1. It's not actually covered by unit tests!  Removing the above
    `foreach` loop doesn't break any unit tests.

 2. While dotnet/android was updated for this scenario, it was only
    as part of trying to use `jnimarshalmethod-gen` on
    Xamarin.Android projects, which was never finished.

 3. It doesn't "scale": the code throws a `NotSupportedException`
    if a type implements more than one interface that has
    `[JniValueMarshaler]`.

This isn't used, and *shouldn't* be relied upon.  Excise it entirely.

With these changes we can remove
`DynamicallyAccessedMemberTypes.Interfaces`.

I also introduced `build-tools/trim-analyzers/trim-analyzers.props`
that will setup the appropriate trimmer MSBuild properties to make
trimmer warnings an error.  This should keep us from accidentally
creating warnings.  I only use this setting in projects that were
already using `$(EnableAotAnalyzer)`.

Context: 8d77130
Context: #9630

We're exploring how to get .NET for Android apps to build and run
using [Native AOT][0].

Default to `$(TrimMode)=Full` for NativeAOT, this enables trimmer
warnings and should be the default mode for NativeAOT.

Ensure the `_PrepareLinking` MSBuild target runs at the appropriate
time.  Failure to do so was causing
`Android.App.Activity.GetOnCreate_Landroid_os_Bundle_Handler()` to be
trimmed away.

Various fixes to avoid `java.lang.UnsatisfiedLinkError` errors:

  * Set `$(LinkerFlavor)=lld` by default to avoid:

        E AndroidRuntime: java.lang.UnsatisfiedLinkError: dlopen failed: cannot locate symbol "__start___modules" referenced by
          "/data/app/~~_ggpMC4foLk_jUUycm0CfA==/net.dot.hellonativeaot-fvszIWroqgweLHYgULxVoQ==/split_config.arm64_v8a.apk!/lib/arm64-v8a/libNativeAOT.so"...

  * Include `libc++_shared.so` within the app, as Native AOT output
    requires C++:

        E AndroidRuntime: java.lang.UnsatisfiedLinkError: dlopen failed: library "libc++_shared.so" not found: needed by
          /data/app/~~_W0B9EE3hhajnFvCHyUKSg==/net.dot.hellonativeaot-zlXemqHdkbHaLu60oYPVQQ==/lib/arm64/libNativeAOT.so in namespace clns-6

Emit `JavaPeerStyle.JavaInterop1` java stubs for NativeAOT, as it is
easier to get working in place of `JavaPeerStyle.XAJavaInterop1`.
Specifically, we need to be able to avoid P/Invokes related to
typemaps/etc.  XAJavaInterop1 hits `JNIEnvInit.RegisterJniNatives()`,
which is full of P/Invokes such as `TypeManager.GetClassName()`,
while `JavaInterop1` hits `ManagedPeer.RegisterNativeMembers()` which
goes through `JniRuntime` abstractions, allowing for a P/Invoke-free
code path.

I updated `BuildTest2.NativeAOT()` to assert for these changes where
possible.

[0]: https://learn.microsoft.com/dotnet/core/deploying/native-aot/